networking documentation changes for engine v29#23362
Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: Rob Murray <rob.murray@docker.com>
Signed-off-by: Rob Murray <rob.murray@docker.com>
With nftables on the way - refer to "firewall" instead of "iptables" in the top-level description of packet-filtering-firewalls, move out the iptables specifics, and port-publishing (which applies to both iptables and nftables). Signed-off-by: Rob Murray <rob.murray@docker.com>
Adds engine/network/firewall-nftables.md Signed-off-by: Rob Murray <rob.murray@docker.com>
Signed-off-by: Rob Murray <rob.murray@docker.com>
Note that nftables support was added in moby29
Signed-off-by: Rob Murray <rob.murray@docker.com>
nftables doc: rename moby 29.0.0 -> Docker 29.0.0
usha-mandya
left a comment
There was a problem hiding this comment.
Thanks for the PR @thaJeztah. I've added some minor suggestion. PTAL
| and further chains are added for each bridge network. The moby project | ||
| has some [internal documentation](https://github.com/moby/moby/blob/master/integration/network/bridge/nftablesdoc/index.md) | ||
| describing its nftables, and how they depend on network and container | ||
| configuration. But, the tables and their rules are likely to change between |
There was a problem hiding this comment.
nit
| configuration. But, the tables and their rules are likely to change between | |
| configuration. However,, the tables and their rules are likely to change between |
| configuration. But, the tables and their rules are likely to change between | ||
| Docker Engine releases. | ||
|
|
||
| Do not modify Docker's tables directly as the modifications are likely to |
| `docker`, it creates a forwarding policy called `docker-forwarding` that | ||
| accepts forwarding from `ANY` zone to the `docker` zone. | ||
|
|
||
| As an example, to use nftables to block forwarding between interfaces `eth0` |
There was a problem hiding this comment.
| As an example, to use nftables to block forwarding between interfaces `eth0` | |
| For example, to use nftables to block forwarding between interfaces `eth0` |
|
|
||
| When Docker Engine on Linux starts for the first time, it has a single | ||
| built-in network called the "default bridge" network. When you run a | ||
| container with no `--network` option, it is connected to the default bridge. |
There was a problem hiding this comment.
nit
| container with no `--network` option, it is connected to the default bridge. | |
| container without the `--network` option, it is connected to the default bridge. |
| ``` | ||
|
|
||
| You can combine `-s` or `--src-range` with `-d` or `--dst-range` to control both | ||
| the source and destination. For instance, if the Docker host has addresses |
There was a problem hiding this comment.
| the source and destination. For instance, if the Docker host has addresses | |
| the source and destination. For example, if the Docker host has addresses |
| $ iptables -I DOCKER-USER -m state --state RELATED,ESTABLISHED -j ACCEPT | ||
| ``` | ||
|
|
||
| For more detailed information about iptables configuration and advanced usage, |
There was a problem hiding this comment.
| For more detailed information about iptables configuration and advanced usage, | |
| For more information about iptables configuration and advanced usage, |
| > Support for nftables introduced in Docker 29.0.0 is experimental, configuration | ||
| > options, behavior and implementation may all change in future releases. | ||
| > The rules for overlay networks have not yet been migrated from iptables. | ||
| > So, nftables cannot be enabled when the daemon has Swarm enabled. |
There was a problem hiding this comment.
| > So, nftables cannot be enabled when the daemon has Swarm enabled. | |
| > Therefore, nftables cannot be enabled when the Docker daemon is running in the Swarm mode. |
| } | ||
| ``` | ||
|
|
||
| For more detailed information about nftables configuration and advanced usage, |
There was a problem hiding this comment.
| For more detailed information about nftables configuration and advanced usage, | |
| For more information about nftables configuration and advanced usage, |
| keywords: network, iptables, firewall | ||
| --- | ||
|
|
||
| By default, for both IPv4 and IPv6, the daemon blocks access to ports that have not |
There was a problem hiding this comment.
| By default, for both IPv4 and IPv6, the daemon blocks access to ports that have not | |
| By default, for both IPv4 and IPv6, the Docker daemon blocks access to ports that have not |
|
Thanks @usha-mandya - I can pick these up ... I'll add another PR to the branch, for the PR to merge. |
Signed-off-by: Rob Murray <rob.murray@docker.com>
|
moby29 networking - address review comments
|
Should this also change the "nft rules are not supported" installation note added in #19618? |
Description
Related issues or tickets
Reviews